The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 30, 2026 3:00am

PR Summary

Medium Risk
Switches the primary read path for all user-facing chat transcripts; mis-ordering or drift from dual-write JSONB would change LLM/history payloads, though shape is unchanged and JSONB remains written.

Overview
User-facing copilot chat loads now build transcripts from copilot_messages instead of detoasting copilot_chats.messages. In lifecycle.ts, loadCopilotChatMessages loads non-deleted rows ordered by seq (NULLS LAST), created_at, and id; getAccessibleCopilotChat and getAccessibleCopilotChatWithMessages stop selecting the JSONB blob, authorize first, then attach the table-backed message list. That path feeds copilot/mothership GETs and resolveOrCreateChat’s conversationHistory; new chats return messages: [] from insert without a messages query.

Adds lifecycle.test.ts for ordering, empty transcripts, auth failures skipping the messages query, legacy getter behavior, and create vs load paths. Dual-write to JSONB is unchanged for other readers.

^{Reviewed by Cursor Bugbot for commit 2e7f4ec. Configure here.}

Greptile Summary

This PR cuts over copilot chat transcript reads from the legacy copilot_chats.messages JSONB column to the normalized copilot_messages table, avoiding the costly TOAST decompression on every chat load while keeping the dual-write intact for fallback and internal-logic reads.

• New loadCopilotChatMessages(chatId) reads from copilot_messages in (seq ASC NULLS LAST, created_at ASC, id ASC) order; both detail getters (getAccessibleCopilotChat, getAccessibleCopilotChatWithMessages) drop messages from the metadata select and call it only after authorization succeeds.
• A separate copilotChatDetailReturningColumns set is introduced for new-chat inserts so a fresh row returns messages: [] directly from the RETURNING clause without issuing a second query.
• New lifecycle.test.ts verifies table-sourced messages, empty transcripts, chat-not-found and auth-denied no-query guards, the legacy getter, and both existing/new paths in resolveOrCreateChat.

Confidence Score: 5/5

Safe to merge — reads from the normalized table only after authorization succeeds, dual-write and JSONB column are untouched, and pre-cutover integrity was verified on prod.

The change is a well-scoped read-path swap: the JSONB column remains written and available as a fallback, authorization always gates the new messages query, and the normalized table was fully validated against the JSONB source before cutover. The implementation is clean, the tests exercise the critical invariants (including the auth-denied no-query contract added in the head SHA), and the type-check and full suite pass.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Caller
    participant getAccessibleCopilotChatWithMessages
    participant copilot_chats DB
    participant authorizeCopilotChatRow
    participant loadCopilotChatMessages
    participant copilot_messages DB

    Caller->>getAccessibleCopilotChatWithMessages: (chatId, userId)
    getAccessibleCopilotChatWithMessages->>copilot_chats DB: SELECT metadata columns WHERE id=chatId AND userId=userId LIMIT 1
    copilot_chats DB-->>getAccessibleCopilotChatWithMessages: chat row (no messages JSONB)
    getAccessibleCopilotChatWithMessages->>authorizeCopilotChatRow: (chat, chatId, userId)
    alt not found or auth denied
        authorizeCopilotChatRow-->>getAccessibleCopilotChatWithMessages: null
        getAccessibleCopilotChatWithMessages-->>Caller: null (no messages query)
    else authorized
        authorizeCopilotChatRow-->>getAccessibleCopilotChatWithMessages: authorized row
        getAccessibleCopilotChatWithMessages->>loadCopilotChatMessages: (chatId)
        loadCopilotChatMessages->>copilot_messages DB: SELECT content WHERE chat_id=chatId AND deleted_at IS NULL ORDER BY seq ASC NULLS LAST, created_at ASC, id ASC
        copilot_messages DB-->>loadCopilotChatMessages: [{content}, ...]
        loadCopilotChatMessages-->>getAccessibleCopilotChatWithMessages: "Record<string,unknown>[]"
        getAccessibleCopilotChatWithMessages-->>Caller: "{...authorizedRow, messages}"
    end

_{Reviews (2): Last reviewed commit: "test(copilot): cover auth-deny on a foun..." | Re-trigger Greptile}

@greptile

@cursor review